The committers listed above are authorized under a signed CLA.

• ✅ login: Akshat111111 / name: Akshat Sharma (2138e65, 2326233, 3b24175, 576681b, 7dc62c9, 81d391f, c96b4da, ec5fda3)

@Akshat111111 is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel.

A member of the Team first needs to authorize it.

Thanks for writing this Akshat.

I'll let others comment but my thoughts are that posts on graphql.org should be voiced as a "We", not "I". It'd be OK if this were a testimony but since this is more of a feedback from a community organized event, I'd like it better if it were written from the point of view of the team.

I don't think we have any guidelines around this though so it might be a personal thing. Whatever we decide, we should document in CONTRIBUTING.md

Thanks for writing this Akshat.

I'll let others comment but my thoughts are that posts on graphql.org should be voiced as a "We", not "I". It'd be OK if this were a testimony but since this is more of a feedback from a community organized event, I'd like it better if it were written from the point of view of the team.

I don't think we have any guidelines around this though so it might be a personal thing. Whatever we decide, we should document in CONTRIBUTING.md

Sure! Make sense.

@martinbonnin Martin, I would like to start taking articles written from Ambassadors in their own voice. I want to tag this as an Ambassador story and eventually we would have a number of them we can then spotlight in the Ambassador pages perhaps.

@jemgillam sounds good to me. Suggestion to rename the tag to ambassador stories instead of just ambassadors.

As a reader, I want to be able to filter on content. Just as I wouldn't do a tsc or board tag. Whether the author is a TSC, board member or ambassador is useful context but not the most important one.

I have no idea if the tag can be two words, if so then that is definitely preferred!

I noticed a lint error on the first sub heading, looking back I can see many blog posts don't have a H1 and instead start on using H2 headings. Is this lint rule new? I don't think it's needed for blog content.

I have no idea if the tag can be two words

We have IN THE NEWS so I'm guessing that'll work.

Is this lint rule new? I don't think it's needed for blog content.

Not sure if it's new but agreed we probably don't need it.

Hello @jemgillam
Can this be merged now??

@Akshat111111 It is still failing on a lint rule, but don't make any changes

@benjie any insight into why suddenly articles can't skip an H1 title? Many many other articles have been written skipping straight to using H2. What do we need to change?

@Akshat111111 @jemgillam @benjie are we good for shipping this? This will be good content as we head into GraphQL Day Amsterdam

Never mind, still a bunch of issues. See message below.

@Akshat111111 can you please apply f1ab253 to this branch to fix lint and images? For some reason, I can't push to your branch.

@martinbonnin that patch has some additional unneeded things from the conf website. And I can't tell, did you move the blog post into the right directory?

@jemgillam only the sponsors.tsx modification is unrelated (but it still warns in lint). All the rest is. The post uses new tag and needs new colors.

Also yes, the patch moves the markdown file.

I've pushed Martin's commit onto this PR.

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
graphql-github-io	Error		May 29, 2026 4:26pm

I have fixed the lint error, and formatted the images so they look nice. I've updated the date to today, this should be good to go 👍